5.3
MEDIUM CVSS 3.1
CVE-2025-64718
js-yaml has prototype pollution in merge (<<)
Description

js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).

INFO

Published Date :

Nov. 13, 2025, 4:15 p.m.

Last Modified :

Nov. 13, 2025, 4:15 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2025-64718 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
CVSS 3.1 MEDIUM MITRE-CVE
Solution
Update js-yaml to the latest version or use secure parsing configurations.
  • Update js-yaml to version 4.1.1 or later.
  • Use `--disable-proto=delete` flag if running on Node.js.
  • Ensure Deno is used for parsing untrusted YAML.
  • Validate all parsed YAML inputs.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-64718.

URL Resource
https://github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879
https://github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8m
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-64718 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-64718 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2025-64718 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Nov. 13, 2025

    Action Type Old Value New Value
    Added Description js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
    Added CWE CWE-1321
    Added Reference https://github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879
    Added Reference https://github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8m
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 5.3
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact